Why is the Pipedream Jira tool failing to pass the "summary" field to the Jira API, resulting in a 400 Bad Request error?

Bugs
1

This topic was automatically generated from Slack. You can find the original thread here.

Hi team, we have an urgent bug we’ve encountered in the Pipedream Jira tool in production that is effecting our customers. Could you please assist urgently? Thanks in advance.

Bug: jira-create-issue tool fails to pass the "summary" field to the Jira API

Platform: Pipedream MCP integration (Jira app)
Date: April 23, 2026
Caller: Grw AI (calling Pipedream's Jira tools via MCP)

Issue:
When calling the jira-create-issue tool with a "summary" parameter provided, the field is not being included in the API request body sent to Jira. Jira returns a 400 Bad Request error because "summary" is a required field on issue creation.

Expected behavior:
The summary parameter passed to the tool should be forwarded in the payload to Jira's POST /rest/api/3/issue endpoint.

Actual behavior:
The summary field appears to be dropped before the request reaches Jira, resulting in a 400 error due to the missing required field.

Steps to reproduce:
1. Call the jira-create-issue tool via MCP
2. Provide a valid project key, issue type, and summary value
3. Observe that Jira returns a 400 Bad Request indicating the summary field is missing

Notes:
- Other fields (project, issue type) appear to be passed correctly
- This suggests a mapping issue specifically with the "summary" parameter in the tool's schema or request builder
2

Thanks for reporting, will check it out

3

Thank you !

4

This component has dynamic props, probably the cause of your issue. If you’re using MCP in tools-only mode, then it’s expected that this tool won’t work (we’re working on making the currently incompatible tools .compatible with tools-only mode) Tool Modes - Pipedream

Can you confirm if that’s your use case?

5

Thank you for the quick reply - we’re confirming now

6

Yes I can confirm we’re using tools-only mode because we want our agent to be able to manage the tools itself ideally.

Is your recommendation that we use the subagent approach until you have all tools compatible with tools-only mode?

And do you have an ETA for when all tools will be compatible with tools-only mode?

Thanks

7

No ETA unfortunately. We’ve been working on shipping more and more updated versions of the previously incompatible tools for this use case.

I would recommend either using a different mode, or you can also use our recently shipped v3 MCP (Develop with Pipedream MCP - Pipedream)

This version excludes incompatible tools from the ones available in tools-only mode so that you don’t run into these errors.

8

Thanks - we’ve just migrated to v3. Is there any chance you could prioritize getting the Jira issue-writing tool compatible with tools-only mode? It’s a high-impact action for our customers and we’d really like to have it back. Happy to help test as soon as you have something

9

Could you please create a Github issue with this request? You can send the link to it here afterwards

cc